Release 10.1A: OpenEdge Data Management:
SQL Development

Starting SQL and 4GL brokers

Identify your brokers as either primary or secondary. The primary broker should always be the one with the highest value for -Ma.

For the 4GL broker, invoke PROSERVE with the following:

Use –m3 to start up this 4GL broker.
Set –Ma to the maximum number of 4GL users.
Set –Mpb to the maximum number of servers for this 4GL broker.
Set –ServerType to 4GL.

For example, you would use the following command to start a Progress 4GL primary broker:

proserve Sports2002 -H localhost -S 6001 -ServerType 4GL -n 200 -Mn 7 -Mi 3 -Ma 3 -Mpb 4

proserve Sports2002

Starts the Sports2002 database.

-H localhost

Specifies the machine on which the server runs.

-S 6001

Specifies 6001 as the port number to be used when connecting to a broker process.

-ServerType 4GL

Specifies the server type as 4GL.

-n 200

Limits the number of users to 200.

-Mn 7

Specifies 7 as the maximum number of servers.

-Mi 3

Limits the server to three clients.

-Mpb 4

Restricts the number of servers that can be spawned by the broker to 4.

For the SQL broker, invoke PROSERVE with the following:

Use the –n and –Mn results from the formula above.
Set –Ma to the maximum number of SQL users.
Set –Mpb to the maximum number of servers for this SQL broker.
Set –ServerType to SQL.

For example, you would use the following command to start an OpenEdge SQL secondary broker:

proserve Sports2001 -H localhost -S 6000 -ServerType SQL -n 200 -Mi 6 -Ma 3 -Mpb 2 -m3

proserve Sports2001

Starts the Sports2001 database.

-H localhost

Specifies the machine on which the server runs.

-S 6000

Specifies 6000 as the port number to be used when connecting to a broker process.

-ServerType SQL

Specifies the server type as SQL.

-n 200

Limits the number of users to 200.

-Mi 6

Limits the server to six clients.

-Ma 3

Specifies 3 as the maximum number of servers.

-Mpb 2

Restricts the number of servers that can be spawned by the broker to 2.

-m3

Identifies the SQL broker as the secondary broker.

Establishing an encrypted connection

OpenEdge provides you with the ability to provide a Secure Socket Layer (SSL) connection for OpenEdge SQL and Progress 4GL. SSL provides an authenticated and encrypted peer-to-peer TCP/IP connection. You can establish the SSL connection by using the -ssl startup parameter. For more information on creating SSL brokers, see OpenEdge Getting Started: Core Business Services and OpenEdge Deployment: Startup Command and Parameter Reference .

For more information on managing brokers and startup parameters, see OpenEdge Deployment: Startup Command and Parameter Reference and OpenEdge Data Management: Database Administration .